IBM Works for OS/2 | 1996-12-05 | 41KB | 229 lines
IBM Works OS/2
Copyright (C) Footprint Software Inc. 1993-1994
LASERJET
HP LaserJet 4L
HPLaserJ
RELEASE NOTES for Version 0.55 - Beta-1.
REDWOOD at Version 0.55 is an early Beta. There are no guarentees that anything works. If anything goes wrong, you as a Beta tester assume full responsibility. All that aside, here's what we're trying to achieve.
Changes in V 0.55 - Removed the limit on fields. Added an experimental new user prompter. Added a Y2K countdown clock. The clock is free to individual users.
We want shake down the basic functionality. This Beta comes with a Rexx program, hexdata.cmd, that produces a data file of two records of EBCDIC. The records are 48 bytes long and contain character fields, packed decimal fields and zoned decimal fields. REDWOOD can recognize these fields from their content and characteristics. REDWOOD can produce structure maps and the JCL required to compile or update these stucture maps on a mainframe.
Take a look at the Rexx program, note that the data is encoded in EBCDIC hexadecimal. REDWOOD runs internally in both EBCDIC and ASCII.
A basic REDWOOD run is, 1) analyze the file, 2) select the output mode, 3) produce the output. Much of the configuration features have not been implemented. The core processing is functional.
REDWOOD reads mainframe EBCDIC files, analyzes them, and recreates record layouts in COBOL, PL/I, C/C++, S/370 Assembler, etc. including comments and documentation. At this time, only PL/I, Assembler, Documentation, and C/C++ work. PL/I is more complete than the other formatters.
The output is currently placed in the file sysout.dat. This may change in a future version.
Run through the processing sequence with the test data. After you understand the sequence, you can experiment with it by changing the data encoded in hexdata.cmd . We expect that you will find ways to confuse the analyzer. Note these ways down, send copies of your hexdata.cmd along with your test results. Don't get discouraged. There are lots of analyzer routines that are not active in this version.
Here are some questions that we hope to answer during the Beta.
1) What other date formats should we handle. We have a list of 30 that we are working on. We want your advice on this.
2) Does the processing sequence make sense. We expect REDWOOD users to be professional mainframe programmers or QA or IV&V professionals working closely with professional programmers. We use mainframe jargon on the menus and in the documentation because that is the language of our user base. If terms like JCL, VTOC, DD card, IEBUPDTE, and so forth do not make sense or put you off, you do not have the background to use REDWOOD.
3) How can the output be improved. Which languages should we support? We are considering generating SORT MERGE control cards and control statements for DYL-280, IEBGENER, MARK IV, etc.
Should you be in the REDWOOD Beta program?
This is an important question. We can not do any hand holding or training during the Beta. We have too much coding to do and an extremely tight schedule. We want the Beta to be a success for you and us.
Here are a few reasons for entering the Beta.
If you are a mainframe computer professional and will be involved in re-engineering mainframe applications for Y2K compatibility, you may want to join the Beta to perfect your skills, have an early look at our Y2K re-engineering product, and help hone REDWOOD for solving this problem. Based on our assessment of the Beta reports and suggestions, we may award a few "
HHResearch REDWOOD Y2K Engineer
" certificates.
We have lots of stubs and analyzer routines built into REDWOOD for future capabilities. We will activate these during the Beta program. Your feedback will help us set the priorities.
Companies that join the Beta can also benefit except that we will not issue certificates to companies. Most mainframe companies face an incredible problem. If your company does not recognize the scope of the problem, we are not interested in educating your management or debating this topic. Our position is that Y2K will put some companies out of business. (We have seen an estimate that 40% of U.S. Corporations will fail due to the Y2K problem.) To those companies that recognize the problem, we say, "Come with us, if you want to live." To the others, "Good luck, maybe we'll see you on the other side."
Here are some reasons to avoid the Beta.
We expect to change the User interface. If you are not flexible, you may wish to wait until REDWOOD stabilizes before learning to use it.
We are developing the back side of the Y2K solution. If you are still in the discovery or planning stage of your Y2K effort, you probably shouldn't be in the Beta. There are lots of consulting companies that will help you with a Y2K assessment or provide awareness training. Here's ours, "You have a big problem, that'll be a million dollars please."
Are you ready to Rock 'n Roll?
After you've played with hexdata.cmd a little, you may want to feed live data to REDWOOD.
The Beta will only read 2 logical records.
The Beta only processes flat files with an LRECL=48 and a RECFM of F or FB. You can use IEBGENER to create a subfile suitable for testing.
We will post announcements of the Beta releases on comp.os.os2.announce and comp.software.year-2000. We will release a new Beta every two weeks. We will monitor comp.software.year-2000 and comp.os.os2.advocacy.
(.txt)